Systems Acceptance Testing provides an independent review of the complete product from the customer or end user’s point of view. Depending on the project’s contractual environment, the results of System Acceptance Testing may determine if contract is complete and the customer will accept delivery of the product. Under other environments, Systems Acceptance Testing determines if a product may be shipped to the marketplace.

Systems Acceptance Testing includes two distinct parts: Systems Verification Testing and Systems Validation Testing.

Systems Verification Testing confirms the system components works as specified in the integrated environment. Verification testing confirms that the system meets all of the top-level requirements. These requirements may be Statement of Work Requirements, Customer Requirements, System Requirements, or some equivalent. Frequently, the customer will help specify the test suite and witness the tests’ execution.

Validation Testing confirms that the system works as intended when placed in its intended environment. Validation does not confirm that the product meets the requirements; rather, it confirms that the product requirements correctly defined the need.